Purpose

• Fix Bicep deployment errors when optional module references (e.g., Application Insights, ACR connection, Bing search connections, storage connection) are conditionally deployed but their outputs are still unconditionally referenced.
• Use the Bicep non-null assertion operator (!) on conditional module outputs to satisfy the compiler when accessing .outputs on modules guarded by if conditions.
• Guard output expressions with !empty() checks and empty-string fallbacks so that outputs resolve safely when upstream AI services or project parameters are not provided.
• Wrap ACR role assignments in a concat() pattern to conditionally include the AI project service principal only when AI services are configured.

Files changed

• infra/core/ai/ai-project.bicep – non-null assertions on applicationInsights module outputs
• infra/core/host/acr.bicep – conditional role assignments and connection output
• infra/core/search/bing_custom_grounding.bicep – conditional connection outputs
• infra/core/search/bing_grounding.bicep – conditional connection outputs
• infra/core/storage/storage.bicep – conditional connection output

Does this introduce a breaking change?

• Yes
• No

Pull Request Type

What kind of change does this Pull Request introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Documentation content changes
• Other... Please describe:

How to Test

• Get the code

git clone https://github.com/justinyoo/azd-ai-starter-basic.git
cd azd-ai-starter-basic
git checkout hotfix/conditional-outputs

• Test the code

azd up

What to Check

Verify that the following are valid

• Deployment succeeds when all optional parameters are provided (full deployment)
• Deployment succeeds when AI services account name and project name are omitted (partial deployment)
• No Bicep compiler warnings or errors on the changed files

Other Information